CVE-2026-23367
wifi: radiotap: reject radiotap with unknown bits
Description
In the Linux kernel, the following vulnerability has been resolved: wifi: radiotap: reject radiotap with unknown bits The radiotap parser is currently only used with the radiotap namespace (not with vendor namespaces), but if the undefined field 18 is used, the alignment/size is unknown as well. In this case, iterator->_next_ns_data isn't initialized (it's only set for skipping vendor namespaces), and syzbot points out that we later compare against this uninitialized value. Fix this by moving the rejection of unknown radiotap fields down to after the in-namespace lookup, so it will really use iterator->_next_ns_data only for vendor namespaces, even in case undefined fields are present.
INFO
Published Date :
March 25, 2026, 11:16 a.m.
Last Modified :
April 24, 2026, 6:41 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | MEDIUM | [email protected] |
Solution
- Update the Linux kernel to the latest version.
- Apply vendor-specific patches for radiotap parser.
- Ensure radiotap fields are properly validated.
- Test system stability after update.
Public PoC/Exploit Available at Github
CVE-2026-23367 has a 1 public
PoC/Exploit available at Github.
Go to the Public Exploits tab to see the list.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-23367.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-23367 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-23367
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
DSA and DLA for Debian last 14 days
Python
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-23367 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-23367 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Apr. 24, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Added CWE NVD-CWE-noinfo Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:2.6.34:-:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.19 up to (excluding) 6.19.7 *cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc5:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc6:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc7:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13 up to (excluding) 6.18.17 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.130 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.12.77 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.203 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.167 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 2.6.34.1 up to (excluding) 5.10.253 Added Reference Type kernel.org: https://git.kernel.org/stable/c/129c8bb320a7cef692c78056ef8e89a2a12ba448 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/2a60c588d5d39ad187628f58395c776a97fd4323 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/2f8ceeba670610d66f77def32011f48de951d781 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/6f80f6a60f5d87e5de5fb2732751fce799991c24 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/703fa979badbba83d31cd011606d060bfb8b0d1d Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/c854758abe0b8d86f9c43dc060ff56a0ee5b31e0 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/d1d1d3c50095928624a95b67a6d7ccc3a18f2215 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/e664971759a0e5570b50c6592e58a7f97d55e992 Types: Patch -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Apr. 18, 2026
Action Type Old Value New Value Added Reference https://git.kernel.org/stable/c/6f80f6a60f5d87e5de5fb2732751fce799991c24 Added Reference https://git.kernel.org/stable/c/d1d1d3c50095928624a95b67a6d7ccc3a18f2215 -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Mar. 25, 2026
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: wifi: radiotap: reject radiotap with unknown bits The radiotap parser is currently only used with the radiotap namespace (not with vendor namespaces), but if the undefined field 18 is used, the alignment/size is unknown as well. In this case, iterator->_next_ns_data isn't initialized (it's only set for skipping vendor namespaces), and syzbot points out that we later compare against this uninitialized value. Fix this by moving the rejection of unknown radiotap fields down to after the in-namespace lookup, so it will really use iterator->_next_ns_data only for vendor namespaces, even in case undefined fields are present. Added Reference https://git.kernel.org/stable/c/129c8bb320a7cef692c78056ef8e89a2a12ba448 Added Reference https://git.kernel.org/stable/c/2a60c588d5d39ad187628f58395c776a97fd4323 Added Reference https://git.kernel.org/stable/c/2f8ceeba670610d66f77def32011f48de951d781 Added Reference https://git.kernel.org/stable/c/703fa979badbba83d31cd011606d060bfb8b0d1d Added Reference https://git.kernel.org/stable/c/c854758abe0b8d86f9c43dc060ff56a0ee5b31e0 Added Reference https://git.kernel.org/stable/c/e664971759a0e5570b50c6592e58a7f97d55e992